From: Joey Hess Date: Mon, 29 Sep 2025 15:18:56 +0000 (-0400) Subject: response X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~3^2~48 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=5a7a2585f861b0e74d768c65cc776b5a05b1b04a;p=git-annex.git response --- diff --git a/doc/forum/meaning___34__stale_or_missing_inode_cache__34____63__/comment_1_9657a0979fae0b88f8a9b8fcdd2417de._comment b/doc/forum/meaning___34__stale_or_missing_inode_cache__34____63__/comment_1_9657a0979fae0b88f8a9b8fcdd2417de._comment new file mode 100644 index 0000000000..07e7cefce5 --- /dev/null +++ b/doc/forum/meaning___34__stale_or_missing_inode_cache__34____63__/comment_1_9657a0979fae0b88f8a9b8fcdd2417de._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2025-09-29T15:16:06Z" + content=""" +The inode cache is something git-annex uses internally to keep track of +changes to files. There are some known situations where it can get out of +date, including an upgrade from a v8 repository. Sometimes inodes change +for various reasons, like copying a repository from one filesystem to +another. So this just means that fsck has detected and updated the +information. I would not worry about it unless git-annex has other +unexpected behavior. +"""]]